Skip to content

POC - Enable DO Snap for DU Snap integration#1

Open
Nox-MSFT wants to merge 2 commits intodevelopfrom
du-snap-integration-poc
Open

POC - Enable DO Snap for DU Snap integration#1
Nox-MSFT wants to merge 2 commits intodevelopfrom
du-snap-integration-poc

Conversation

@Nox-MSFT
Copy link
Owner

  • Use separate ('configs') folder for sdk-config.json file. (This is optional)
  • Create content-download-folder plug that can be used for sharing content between DO and DU snap
  • [For testing purposes] Add 'sdk' part in DO snap, so that we can use it for sdk installation, if needed.

const std::string& GetSDKConfigFilePath()
{
#ifdef DO_BUILD_FOR_SNAP
static std::string configFilePath(DO_CONFIG_DIRECTORY_PATH "/configs/sdk-config.json");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather not have different paths like this. Instead, I think it is ok to allow write access to the entire /etc/deliveryoptimization-agent folder.

- libssh-4
- libwind0-heimdal

sdk:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't think we should be including deb file within the snap. Since the recommendation is for DU to include the libDO.so in its own snap, let's keep this snapcraft file for the DO agent alone.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. This is for testing purposes only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants